fix: remove invalid export_compliance parameters from Fastlane #64
+2
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove export_compliance_uses_encryption (invalid parameter) - Remove export_compliance_is_exempt (invalid parameter) - Remove export_compliance_platform (invalid parameter) - Remove export_compliance_compliance_required (invalid parameter) - Remove export_compliance_app_type (invalid parameter) - Remove export_compliance_encryption_updated (invalid parameter) - Remove export_compliance_contains_third_party_cryptography (invalid parameter) - Keep only uses_non_exempt_encryption (valid parameter) The upload_to_testflight action only accepts uses_non_exempt_encryption for export compliance, not the export_compliance_* parameters.
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a critical Fastlane configuration issue that was causing the iOS release pipeline to fail during TestFlight uploads. The problem stemmed from using invalid export_compliance_* parameters that are not supported by the upload_to_testflight action.
Key Changes:
- Removed all invalid
export_compliance_*parameters from the Fastfile - Retained only the valid
uses_non_exempt_encryption: falseparameter - Simplified the export compliance configuration to use only supported options
Code Coverage Report ❌Current coverage: 19.54% |
Member
Author
|
Closing this PR in favor of #65 which provides a more complete solution by reverting to the stable Oct 10 configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The iOS Release Pipeline is failing with the error:
Root Cause
The Fastlane
upload_to_testflightaction only acceptsuses_non_exempt_encryptionfor export compliance configuration. Theexport_compliance_*parameters are not valid options.Solution
Removed all invalid
export_compliance_*parameters:export_compliance_uses_encryptionexport_compliance_is_exemptexport_compliance_platformexport_compliance_compliance_requiredexport_compliance_app_typeexport_compliance_encryption_updatedexport_compliance_contains_third_party_cryptographyKept only the valid parameter:
uses_non_exempt_encryption: falseTesting
This fix will allow the TestFlight upload to complete successfully. The Info.plist already contains
ITSAppUsesNonExemptEncryption = falsewhich handles the export compliance at the binary level.Related